home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-06
/
fyi14.zip
/
02051.DOS
< prev
next >
Wrap
Text File
|
1991-02-05
|
2KB
|
47 lines
Number: A1TH010291U1768
Subject: Abend Problems with Disk Duplexing and NetWare 386 v3.10a
Date: December 29, 1991
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
GENERAL
INFORMATION: NetWare 386 v3.10a
386a file server with 2 DCBs and 4 embedded SCSI drives
PROBLEM: A test was set up in the lab using this configuration. A
problem was encountered when going into MONITOR and select
DISK INFORMATION and trying to select the drive that has
gone down. It Abends the file server. It did this no
matter which drive went down.
COMMENTS: This test was done by pulling the power cable off the drive.
Another test was setup using a slightly different
configuration. The duplexing was done between a Channel 0
MFM controller and a Channel 2 DCB, and a Channel 1 DCB with
a Channel 2 DCB. A workstation was set up running a batch
file that copied files to the duplexed drives in an infinite
loop. This is a table of test results when accessing the
disk information in MONITOR after crashing the duplexed
drive:
Duplexed Pairs Method Results
MFM CH0 and DCB CH2 Pulled data cable No Abend, kept running
MFM CH0 and DCB CH2 Pulled power cord No Abend, kept running
DCB CH1 and DCB CH2 Pulled data cable No Abend, kept running
DCB CH1 and DCB CH2 Pulled power cord Abend or 386 debugger
In a production environment, usually something mechanical on
the drive goes wrong or some of the circuitry fails. The
result is seriously corrupted data which causes the drive to
crash. For this reason it is probably wiser to pull the
data cable when simulating a drive crashing.
Pulling the power cord may simulate a power outage. Except
that in most cases the file server is on the same power line
as the subsystem or internal drive. So both the file server
and drives go down when the power goes out.
(X) This information was verified in the lab.